I solved it, was looking through some of the old documents i had written and came across an old Retropie.txt file i created years ago which i had written myself an old guide on how to set up the network rom shares. In the fstab i had used the following.

//IP/Gaming/RetroPie /home/pi/RetroPie cifs username=pi,password=***********,uid=3001,gid=3001,nounix,noserverino,rw,user,exec 0 0

I had totally forgot that i just had to give the pi read/write access to the Gaming dataset and then in fstab i just needed to drop in the uid, gid and rw and it now saves.

Cheers

@sirhenrythe5th Awesome! Thank you for this response. It will be very helpful in getting rid of some of the systems I don't intend on playing on my arcade cabinet! Thank you again!!

@wtstreetglow1 It looks like reversing the slashes on the first (windows) share got this working.

It should have been:

//WESTONSPC/roms

@mitu

I figured it out!

Turns out, the zip contained .unh files, which is not supported. I've got some new files and it's up and running. As of n64, I had to unzip each file to get them to run.

Bonus question: is there something I can do to get n64 to run more smooth (rpi 3 B+)?

Again, thanks for taking your time. And for future googlers, hope this help you out.

@mitu great, thanks. pi user password has already been changed from the default password. I'd say we can mark this help and support forum question to complete/resolved. Appreciate the help.

@TrisM Though it is an old thread and I haven't asked/wondered aloud back over nearly 2 years ago, was considering it to be just a SEP. But as you revoked revived the thread I am doing it now, because now I am really puzzled/curious and doubting again: I have Windows 10 Pro on 2 desktop + 1 laptop machines since the EOL of Window 7 and a third desktop setup in 2020. None of them had this behaviour and on all four (3 on 22H2, my laptop still on 21H2) this Group Policy is still defaulting to "Not configured" [edit: besides Mitus remark in the early posts that it is disabled as default on some mints of win10 and that's not including home/pro] . And as Win10 is using "Language Packs" (as it was on xp x64) instead of regional versions of the os itself, I somehow doubt that updates are meddling with those settings differently for different regions and I am still unsure why this was changed on some user systems and whether it truly was done by the M$ Update or by other means and if yes under what circumstances this would have happened.

@vodkanakas Thanks for sharing your solution for others who might encounter the same problem. 👍

I had issues with Pi4 wifi too. In my case I was noticing it when sending files over Samba from W10 or using FTP, and also scraping problems. I'd get constant disconnects and transfer speeds of around 200kb/s even when it would stay working.

I found mentions online of known issues where noise from the HDMI output can disrupt the wifi signal. Every instance I saw talked about said it was only over a certain resolution (1440 I think), but I decided to try disconnecting my 5" screen anyway, which runs 800x480, and as soon as I did that the speeds went up to around 3-5MB/s and the connection stays stable.

I removed the Windows features for old SMB, rebooted, tried mapping with IP and it worked. Thanks!

@Clyde said in Storing ROMs and other data on a remote drive:

You can set it in the file /home/pi/.emulationstation/es_settings.cfg via the line <bool name="ParseGamelistOnly" value="true" />.

Finally got around to try that out. I didn't notice any real difference in starting time. It spends 80%-ish of the EmulationStation load screen with "Loading system config". The total time from console to be in the UI is ~1 minute regardless if ParseGamelistOnly is set to true or false.

It might be my setup, because there's no es_settings.cfg file available so I had to create it myself:

<?xml version="1.0"?> <bool name="ParseGamelistOnly" value="true" />

@mitu edit. I had a / rather than a comma. No error..

That it working now 👍

OK, works when i mount with option uid=1000 in autofs.network. Thanks for the hint.

@henryjfry said in Certain systems dont work from NFS share:

Would adding async to my fstab improve things do you think?

The async option would be ok, but I don't know if it would solve anything. You can just try different mount options - the less mount options you have, the easier it would be to test different combinations.

Ok, thanks.

I found a script to cleanup gamelist.xml files in emulationstation. I think I'll give it a go.

Thanks for your help!

@mitu great!, thank you so much (another time 😊) Mitu!
I searched the Internet before asking here, but did not find such an answer that really explains it.

Thx Sir and have a nice sunday evening!

You can get a set of verified mount options from the docs. Try it - in your /etc/fstab file - and see if work with those options.

Yeah, the \\IP-ADDRESS-HERE\McArcade\RetroPie\ROMs\Nintendo\Super Nintendo Entertainment System UNC style paths are Windows specific, they won't work on Linux. Glad you got it working, happy gaming !

Today I tried again with a new reflashed image on my pi zero w, I just added Wifi and autostart.sh entry and it worked fine. Guess I will just start over with my pi 3 to get the actual system running from network.

Thank you for your support

@2fst4u
You can use the fstab to mount server shares on availability as well but I have never done this. Nor have I learned about layering filesystems.
the ubuntu fstab help page, example
//server/share /media/samba cifs user=user,uid=1000,gid=100 0 0